fix: preserve docs outbound link placement in analytics - #264

What Problem This Solves

Docs reports cannot distinguish the same outbound destination selected from the community invitation, footer, and article using a single event.

User Impact

Operators can report public content selections by destination and placement. The site UI and native outbound click counts remain unchanged; historical missing fields remain unknown.

Why This Change Was Made

Enrich the existing selection event with query/fragment-free destination URL and hostname for external HTTP(S) anchors, including links to other OpenClaw sites. Preserve existing content IDs and fixed placements. Include the public Edit source and Raise issue anchors through the same handler, while retaining private-panel and browser-privacy guards.

Evidence

• All 287 repository tests pass.
• Focused actual Google SDK fixtures pass with every collection request intercepted: the same Discord destination retains three distinct placements, one selection and one native click per action; native click remains unmodified.
• Cross-site linker behavior, query/fragment stripping, same-origin and non-anchor omissions, rejected targets, private-panel suppression and no replay pass. Separate GPC/DNT fixtures load no SDK and collect no events.
• Autoreview is clean: no accepted or actionable findings.
• No production QA events or Google settings/registration changes.